Support for loading/editing/saving .NET Core single file publish bundles. (#16) #49
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
its0x08
approved these changes
Apr 21, 2022
|
This feature will not make it into dnSpyEx 6.2. I severely underestimated the difficulty of properly implementing this feature. Furthermore, I kind of lost interest in implementing this feature so for now it will be placed on hold. Sorry! |
ElektroKill
force-pushed
the
feature/single-file-bundles
branch
from
7841ec9 to
b5f28de
Compare
ElektroKill
force-pushed
the
feature/single-file-bundles
branch
from
b5f28de to
073864d
Compare
|
Any progress or any coming back for interest? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to bring support for loading, editing, and saving .NET Core single file bundles.
Current implementation status:
dnSpy is able to display assembly entries of bundles and allows editing and saving said assemblies (excluding hex editor).
Roadmap:
Some of these regular dnSpy features require the file to be present in the filesystem. An example of such a feature is the Hex editor. I'm still debating whether support for this feature should be left out or should we write the extracted bundle entries to disk in a temporary location.
fixes #16